Apparatus, system and method of communicating in a neighbor awareness networking cluster

ABSTRACT

Some demonstrative embodiments include apparatuses, systems and/or methods of communicating in an awareness cluster. For example, an apparatus may include circuitry configured to cause an awareness networking device to communicate during one or more Discovery Windows (DW) of an awareness cluster; communicate with one or more devices of at least one data path group, the data path group comprising devices of the awareness cluster and having a common schedule of radio resources (SRR); and communicate with one or more devices of at least one service data group, the service data group comprising devices of the data path group being subscribed to a common service.

CROSS REFERENCE

This application claims the benefit of and priority from U.S.Provisional Patent Application No. 62/115,277 entitled “Apparatus,System and Method of Communicating in An Awareness Cluster”, filed Feb.12, 2015, the entire disclosure of which is incorporated herein byreference.

TECHNICAL FIELD

Embodiments described herein generally relate to communicating in anawareness cluster.

BACKGROUND

Awareness networking, for example, according to a Wireless Fidelity(Wi-Fi) Aware Specification, may enable wireless devices, for example,Wi-Fi devices, to perform device/service discovery, e.g., in their closeproximity.

The awareness networking may include forming a cluster, e.g., a Wi-FiAware cluster, for devices in proximity. Devices in the same Wi-Fi Awarecluster may be configured to follow the same time schedule, e.g., adiscovery window (DW), for example, to facilitate cluster formationand/or to achieve low power operation.

BRIEF DESCRIPTION OF THE DRAWINGS

For simplicity and clarity of illustration, elements shown in thefigures have not necessarily been drawn to scale. For example, thedimensions of some of the elements may be exaggerated relative to otherelements for clarity of presentation. Furthermore, reference numeralsmay be repeated among the figures to indicate corresponding or analogouselements. The figures are listed below.

FIG. 1 is a schematic block diagram illustration of a system, inaccordance with some demonstrative embodiments.

FIG. 2 is a schematic illustration of a network architecture, inaccordance with some demonstrative embodiments.

FIG. 3 is a schematic illustration of timing and frequency schedules offirst and second service data groups, in accordance with somedemonstrative embodiments.

FIG. 4 is a schematic illustration of timing and frequency schedules offirst and second service data groups, in accordance with somedemonstrative embodiments.

FIG. 5 is schematic illustration of relationships between a service datagroup, a data path group, and a cluster, in accordance with somedemonstrative embodiments.

FIG. 6 is a schematic flow-chart illustration of a method ofcommunicating in an awareness cluster, in accordance with somedemonstrative embodiments.

FIG. 7 is a schematic illustration of a product, in accordance with somedemonstrative embodiments.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth in order to provide a thorough understanding of some embodiments.However, it will be understood by persons of ordinary skill in the artthat some embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components, unitsand/or circuits have not been described in detail so as not to obscurethe discussion.

Discussions herein utilizing terms such as, for example, “processing”,“computing”, “calculating”, “determining”, “establishing”, “analyzing”,“checking”, or the like, may refer to operation(s) and/or process(es) ofa computer, a computing platform, a computing system, or otherelectronic computing device, that manipulate and/or transform datarepresented as physical (e.g., electronic) quantities within thecomputer's registers and/or memories into other data similarlyrepresented as physical quantities within the computer's registersand/or memories or other information storage medium that may storeinstructions to perform operations and/or processes.

The terms “plurality” and “a plurality”, as used herein, include, forexample, “multiple” or “two or more”. For example, “a plurality ofitems” includes two or more items.

References to “one embodiment”, “an embodiment”, “demonstrativeembodiment”, “various embodiments” etc., indicate that the embodiment(s)so described may include a particular feature, structure, orcharacteristic, but not every embodiment necessarily includes theparticular feature, structure, or characteristic. Further, repeated useof the phrase “in one embodiment” does not necessarily refer to the sameembodiment, although it may.

As used herein, unless otherwise specified the use of the ordinaladjectives “first”, “second”, “third” etc., to describe a common object,merely indicate that different instances of like objects are beingreferred to, and are not intended to imply that the objects so describedmust be in a given sequence, either temporally, spatially, in ranking,or in any other manner.

Some embodiments may be used in conjunction with devices and/or networksoperating in accordance with existing Wireless Fidelity (WiFi) Alliance(WFA) Specifications (including Wi-Fi Neighbor Awareness Networking(NAN) Technical Specification, Version 1.0, May 1, 2015) and/or futureversions and/or derivatives thereof, devices and/or networks operatingin accordance with existing WFA Peer-to-Peer (P2P) specifications (WiFiP2P technical specification, version 1.5, Aug. 4, 2014) and/or futureversions and/or derivatives thereof, devices and/or networks operatingin accordance with existing Wireless-Gigabit-Alliance (WGA)specifications (Wireless Gigabit Alliance, Inc WiGig MAC and PHYSpecification Version 1.1, April 2011, Final specification) and/orfuture versions and/or derivatives thereof, devices and/or networksoperating in accordance with existing IEEE 802.11 standards (IEEE802.11-2012, IEEE Standard for Information technology—Telecommunicationsand information exchange between systems Local and metropolitan areanetworks—Specific requirements Part 11: Wireless LAN Medium AccessControl (MAC) and Physical Layer (PHY) Specifications, Mar. 29, 2012;IEEE802.11ac-2013 (“IEEE P802.11ac-2013, IEEE Standard for InformationTechnology—Telecommunications and Information Exchange BetweenSystems—Local and Metropolitan Area Networks—Specific Requirements—Part11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)Specifications—Amendment 4: Enhancements for Very High Throughput forOperation in Bands below 6 GHz”, December, 2013); IEEE 802.11ad (“IEEEP802.11ad-2012, IEEE Standard for InformationTechnology—Telecommunications and Information Exchange BetweenSystems—Local and Metropolitan Area Networks—Specific Requirements—Part11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)Specifications—Amendment 3: Enhancements for Very High Throughput in the60 GHz Band”, 28 Dec., 2012); and/or IEEE-802.11REVmc (“IEEE802.11—REVmc™/D3.0, June 2014 draft standard for Informationtechnology—Telecommunications and information exchange between systemsLocal and metropolitan area networks Specific requirements; Part 11:Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)Specification”)) and/or future versions and/or derivatives thereof,devices and/or networks operating in accordance with existing cellularspecifications and/or protocols, e.g., 3rd Generation PartnershipProject (3GPP), 3GPP Long Term Evolution (LTE) and/or future versionsand/or derivatives thereof, units and/or devices which are part of theabove networks, and the like.

Some embodiments may be used in conjunction with one way and/or two-wayradio communication systems, cellular radio-telephone communicationsystems, a mobile phone, a cellular telephone, a wireless telephone, aPersonal Communication Systems (PCS) device, a PDA device whichincorporates a wireless communication device, a mobile or portableGlobal Positioning System (GPS) device, a device which incorporates aGPS receiver or transceiver or chip, a device which incorporates an RFIDelement or chip, a Multiple Input Multiple Output (MIMO) transceiver ordevice, a Single Input Multiple Output (SIMO) transceiver or device, aMultiple Input Single Output (MISO) transceiver or device, a devicehaving one or more internal antennas and/or external antennas, DigitalVideo Broadcast (DVB) devices or systems, multi-standard radio devicesor systems, a wired or wireless handheld device, e.g., a Smartphone, aWireless Application Protocol (WAP) device, or the like.

Some embodiments may be used in conjunction with one or more types ofwireless communication signals and/or systems, for example, RadioFrequency (RF), Infra Red (IR), Frequency-Division Multiplexing (FDM),Orthogonal FDM (OFDM), Orthogonal Frequency-Division Multiple Access(OFDMA), FDM Time-Division Multiplexing (TDM), Time-Division MultipleAccess (TDMA), Multi-User MIMO (MU-MIMO), Extended TDMA (E-TDMA),General Packet Radio Service (GPRS), extended GPRS, Code-DivisionMultiple Access (CDMA), Wideband CDMA (WCDMA), CDMA 2000, single-carrierCDMA, multi-carrier CDMA, Multi-Carrier Modulation (MDM), DiscreteMulti-Tone (DMT), Bluetooth®, Global Positioning System (GPS), Wi-Fi,Wi-Max, ZigBee™, Ultra-Wideband (UWB), Global System for Mobilecommunication (GSM), 2G, 2.5G, 3G, 3.5G, 4G, Fifth Generation (5G)mobile networks, 3GPP, Long Term Evolution (LTE), LTE advanced, EnhancedData rates for GSM Evolution (EDGE), or the like. Other embodiments maybe used in various other devices, systems and/or networks.

The term “wireless device”, as used herein, includes, for example, adevice capable of wireless communication, a communication device capableof wireless communication, a communication station capable of wirelesscommunication, a portable or non-portable device capable of wirelesscommunication, or the like. In some demonstrative embodiments, awireless device may be or may include a peripheral that is integratedwith a computer, or a peripheral that is attached to a computer. In somedemonstrative embodiments, the term “wireless device” may optionallyinclude a wireless service.

The term “communicating” as used herein with respect to a communicationsignal includes transmitting the communication signal and/or receivingthe communication signal. For example, a communication unit, which iscapable of communicating a communication signal, may include atransmitter to transmit the communication signal to at least one othercommunication unit, and/or a communication receiver to receive thecommunication signal from at least one other communication unit. Theverb communicating may be used to refer to the action of transmitting orthe action of receiving. In one example, the phrase “communicating asignal” may refer to the action of transmitting the signal by a firstdevice, and may not necessarily include the action of receiving thesignal by a second device. In another example, the phrase “communicatinga signal” may refer to the action of receiving the signal by a firstdevice, and may not necessarily include the action of transmitting thesignal by a second device.

Some demonstrative embodiments may be used in conjunction with a WLAN,e.g., a wireless fidelity (WiFi) network. Other embodiments may be usedin conjunction with any other suitable wireless communication network,for example, a wireless area network, a “piconet”, a WPAN, a WVAN andthe like.

The term “antenna”, as used herein, may include any suitableconfiguration, structure and/or arrangement of one or more antennaelements, components, units, assemblies and/or arrays. In someembodiments, the antenna may implement transmit and receivefunctionalities using separate transmit and receive antenna elements. Insome embodiments, the antenna may implement transmit and receivefunctionalities using common and/or integrated transmit/receiveelements. The antenna may include, for example, a phased array antenna,a single element antenna, a set of switched beam antennas, and/or thelike.

The phrase “peer to peer (PTP) communication”, as used herein, mayrelate to device-to-device communication over a wireless link(“peer-to-peer link”) between devices. The PTP communication mayinclude, for example, a WiFi Direct (WFD) communication, e.g., a WFDPeer to Peer (P2P) communication, wireless communication over a directlink within a QoS basic service set (BSS), a tunneled direct-link setup(TDLS) link, a STA-to-STA communication in an independent basic serviceset (IBSS), or the like.

Some demonstrative embodiments are described herein with respect to WiFicommunication. However, other embodiments may be implemented withrespect to any other communication scheme, network, standard and/orprotocol.

Reference is now made to FIG. 1, which schematically illustrates a blockdiagram of a system 100, in accordance with some demonstrativeembodiments.

As shown in FIG. 1, in some demonstrative embodiments system 100 mayinclude a wireless communication network including one or more wirelesscommunication devices, e.g., wireless communication devices 102, 115,140, 150, 160, 170 and/or 180.

In some demonstrative embodiments, wireless communication devices 102,115, 140, 150, 160, 170 and/or 180 may include, for example, a UE, anMD, a STA, an AP, a PC, a desktop computer, a mobile computer, a laptopcomputer, an Ultrabook™ computer, a notebook computer, a tabletcomputer, a server computer, a handheld computer, a handheld device, anInternet of Things (IoT) device, a sensor device, a PDA device, ahandheld PDA device, an on-board device, an off-board device, a hybriddevice (e.g., combining cellular phone functionalities with PDA devicefunctionalities), a consumer device, a vehicular device, a non-vehiculardevice, a mobile or portable device, a non-mobile or non-portabledevice, a mobile phone, a cellular telephone, a PCS device, a PDA devicewhich incorporates a wireless communication device, a mobile or portableGPS device, a DVB device, a relatively small computing device, anon-desktop computer, a “Carry Small Live Large” (CSLL) device, an UltraMobile Device (UMD), an Ultra Mobile PC (UMPC), a Mobile Internet Device(MID), an “Origami” device or computing device, a device that supportsDynamically Composable Computing (DCC), a context-aware device, a videodevice, an audio device, an A/V device, a Set-Top-Box (STB), a Blu-raydisc (BD) player, a BD recorder, a Digital Video Disc (DVD) player, aHigh Definition (HD) DVD player, a DVD recorder, a HD DVD recorder, aPersonal Video Recorder (PVR), a broadcast HD receiver, a video source,an audio source, a video sink, an audio sink, a stereo tuner, abroadcast radio receiver, a flat panel display, a Personal Media Player(PMP), a digital video camera (DVC), a digital audio player, a speaker,an audio receiver, an audio amplifier, a gaming device, a data source, adata sink, a Digital Still camera (DSC), a media player, a Smartphone, atelevision, a music player, or the like.

In some demonstrative embodiments, one or more devices of wirelesscommunication devices 102, 115, 140, 150, 160, 170 and/or 180, e.g.,device 140, may include, or may perform the functionality of, an AccessPoint (AP), e.g., as described below.

For example, the AP may include a router, a PC, a server, a Hot-Spotand/or the like.

In some demonstrative embodiments, one or more devices of wirelesscommunication devices 102, 115, 140, 150, 160, 170 and/or 180, e.g.,device 102, may perform the functionality of a non-AP STA, and/or device140 may perform the functionality of an AP STA.

In one example, a station (STA) may include a logical entity that is asingly addressable instance of a medium access control (MAC) andphysical layer (PHY) interface to the wireless medium (WM). The STA mayperform any other additional or alternative functionality.

In one example, an AP may include an entity that contains a station(STA), e.g., one STA, and provides access to distribution services, viathe wireless medium (WM) for associated STAs. The AP may perform anyother additional or alternative functionality.

In one example, a non-access-point (non-AP) station (STA) may include aSTA that is not contained within an AP. The non-AP STA may perform anyother additional or alternative functionality.

In some demonstrative embodiments, devices 102, 115, 140, 150, 160, 170and/or 180 may include, for example, one or more of a processor 191, aninput unit 192, an output unit 193, a memory unit 194, and/or a storageunit 195. Devices 102, 115, 140, 150, 160, 170 and/or 180 may optionallyinclude other suitable hardware components and/or software components.In some demonstrative embodiments, some or all of the components ofdevices 102, 115, 140, 150, 160, 170 and/or 180 may be enclosed in acommon housing or packaging, and may be interconnected or operablyassociated using one or more wired or wireless links. In otherembodiments, components of devices 102, 115, 140, 150, 160, 170 and/or180 may be distributed among multiple or separate devices.

In some demonstrative embodiments, processor 191 may include, forexample, a Central Processing Unit (CPU), a Digital Signal Processor(DSP), one or more processor cores, a single-core processor, a dual-coreprocessor, a multiple-core processor, a microprocessor, a hostprocessor, a controller, a plurality of processors or controllers, achip, a microchip, one or more circuits, circuitry, a logic unit, anIntegrated Circuit (IC), an Application-Specific IC (ASIC), or any othersuitable multi-purpose or specific processor or controller. Processor191 executes instructions, for example, of an Operating System (OS) ofdevice 102 and/or of one or more suitable applications.

In some demonstrative embodiments, Input unit 192 may include, forexample, a keyboard, a keypad, a mouse, a touch-screen, a touch-pad, atrack-ball, a stylus, a microphone, or other suitable pointing device orinput device. Output unit 193 includes, for example, a monitor, ascreen, a touch-screen, a flat panel display, a Light Emitting Diode(LED) display unit, a Liquid Crystal Display (LCD) display unit, aplasma display unit, one or more audio speakers or earphones, or othersuitable output devices.

In some demonstrative embodiments, memory unit 194 may include, forexample, a Random Access Memory (RAM), a Read Only Memory (ROM), aDynamic RAM (DRAM), a Synchronous DRAM (SD-RAM), a flash memory, avolatile memory, a non-volatile memory, a cache memory, a buffer, ashort term memory unit, a long term memory unit, or other suitablememory units. Storage unit 195 includes, for example, a hard disk drive,a floppy disk drive, a Compact Disk (CD) drive, a CD-ROM drive, a DVDdrive, or other suitable removable or non-removable storage units.Memory unit 194 and/or storage unit 195, for example, may store dataprocessed by device 102.

In some demonstrative embodiments, wireless communication devices 102,115, 140, 150, 160, 170 and/or 180 may be capable of communicatingcontent, data, information and/or signals via a wireless medium (WM)103. In some demonstrative embodiments, wireless medium 103 may include,for example, a radio channel, a cellular channel, a Global NavigationSatellite System (GNSS) Channel, an RF channel, a Wireless Fidelity(WiFi) channel, an IR channel, a Bluetooth (BT) channel, and the like.

In some demonstrative embodiments, wireless communication medium 103 mayinclude a wireless communication channel over a 2.4 Gigahertz (GHz)frequency band, a 5 GHz frequency band, a millimeterWave (mmWave)frequency band, e.g., a 60 GHz frequency band, a Sub 1 Gigahertz (S1G)band, and/or any other frequency band.

In some demonstrative embodiments, devices 102, 115, 140, 150, 160, 170and/or 180 may include one or more radios including circuitry and/orlogic to perform wireless communication between devices 102, 115, 140,150, 160, 170, 180 and/or one or more other wireless communicationdevices. For example, devices 102, 115, 140, 150, 160, 170 and/or 180may include a radio 114.

In some demonstrative embodiments, radio 114 may include one or morewireless receivers (Rx) including circuitry and/or logic to receivewireless communication signals, RF signals, frames, blocks, transmissionstreams, packets, messages, data items, and/or data. For example, radio114 may include a receiver 116.

In some demonstrative embodiments, radio 114 may include one or morewireless transmitters (Tx) including circuitry and/or logic to sendwireless communication signals, RF signals, frames, blocks, transmissionstreams, packets, messages, data items, and/or data. For example, radio114 may include a transmitter 118.

In some demonstrative embodiments, radio 114 may be configured tocommunicate over a 2.4 GHz band, a 5 GHz band, a mmWave band, a S1Gband, and/or any other band.

In some demonstrative embodiments, radio 114 may include circuitryand/or logic, modulation elements, demodulation elements, amplifiers,analog to digital and digital to analog converters, filters, and/or thelike. In one example, radio 114 may include or may be implemented aspart of a wireless Network Interface Card (NIC), and the like.

In some demonstrative embodiments, radio 114 may include, or may beassociated with, one or more antennas 107.

In one example, device 102 may include a single antenna 107. In otherexample, device 102 may include two or more antennas 107.

Antennas 107 may include any type of antennas suitable to transmitand/or receive wireless communication signals, blocks, frames,transmission streams, packets, messages and/or data. For example,antennas 107 may include any suitable configuration, structure and/orarrangement of one or more antenna elements, components, units,assemblies and/or arrays. Antennas 107 may include, for example,antennas suitable for directional communication, e.g., using beamformingtechniques. For example, antennas 107 may include a phased arrayantenna, a multiple element antenna, a set of switched beam antennas,and/or the like. In some embodiments, antennas 107 may implementtransmit and receive functionalities using separate transmit and receiveantenna elements. In some embodiments, antennas 107 may implementtransmit and receive functionalities using common and/or integratedtransmit/receive elements.

In some demonstrative embodiments, wireless communication devices 102,115, 140, 150, 160, 170 and/or 180 may form, and/or may communicate aspart of, a wireless local area network (WLAN).

In some demonstrative embodiments, wireless communication devices 102,115, 140, 150, 160, 170 and/or 180 may form, and/or may communicate aspart of, a WiFi network.

In some demonstrative embodiments, wireless communication devices 102,115, 140, 150, 160, 170 and/or 180 may form, and/or may communicate aspart of, a WiFi Direct (WFD) network, e.g., a WiFi direct services(WFDS) network, and/or may perform the functionality of one or more WFDdevices.

In one example, wireless communication devices 102, 115, 140, 150, 160,170 and/or 180 may include, or may perform the functionality of a WiFiDirect device.

In some demonstrative embodiments, wireless communication devices 102,115, 140, 150, 160, 170 and/or 180 may be capable of performingawareness networking communications, for example, according to anawareness protocol, e.g., a WiFi aware protocol, and/or any otherprotocol, e.g., as described below.

In some demonstrative embodiments, wireless communication devices 102,115, 140, 150, 160, 170 and/or 180 may be capable of forming, and/orcommunicating as part of, a Neighbor Awareness Networking (NAN) network,e.g., a WiFi NAN or WiFi Aware network, and/or may perform thefunctionality of one or more NAN devices (“WiFi aware devices”).

In some demonstrative embodiments, wireless communication medium 103 mayinclude a direct link, for example, a PTP link, e.g., a WiFi direct P2Plink or any other PTP link, for example, to enable direct communicationbetween wireless communication devices 102, 115, 140, 150, 160, 170and/or 180.

In some demonstrative embodiments, wireless communication devices 102,115, 140, 150, 160, 170 and/or 180 may perform the functionality of WFDP2P devices. For example, devices 102, 115, 140, 150, 160, 170 and/or180 may be able to perform the functionality of a P2P client device,and/or P2P group Owner (GO) device.

In other embodiments, wireless communication devices 102, 115, 140, 150,160, 170 and/or 180 may form, and/or communicate as part of, any othernetwork and/or perform the functionality of any other wireless devicesor stations.

In some demonstrative embodiments, devices 102, 115, 140, 150, 160, 170and/or 180 may include one or more applications configured to provide,share, and/or to use one or more services, e.g., a social application, afile sharing application, a media application and/or the like, forexample, using an awareness network, NAN network (“WiFi Aware network”),a PTP network, a P2P network, WFD network, or any other network.

In some demonstrative embodiments, device 102 may execute an application125 and/or an application 126.

In some demonstrative embodiments, devices 102, 115, 140, 150, 160, 170and/or 180 may be capable of sharing, showing, sending, transferring,printing, outputting, providing, synchronizing, and/or exchangingcontent, data, and/or information, e.g., between applications and/orservices of devices 102, 115, 140, 150, 160, 170 and/or 180 and/or oneor more other devices.

In some demonstrative embodiments, devices 102, 115, 140, 150, 160, 170and/or 180 may include a controller configured to control one or morefunctionalities of devices 102, 115, 140, 150, 160, 170 and/or 180, forexample, one or more functionalities of communication, e.g., awarenessnetworking communications, WiFi Aware (NAN) communication and/or anyother communication, between devices 102, 115, 140, 150, 160, 170 and/or180 and/or other devices, and/or any other functionality, e.g., asdescribed below. For example, device 102 may include a controller 124.

In some demonstrative embodiments, controller 124 may be configured toperform one or more functionalities, communications, operations and/orprocedures between wireless communication devices 102, 115, 140, 150,160, 170 and/or 180, and/or one or more other devices, e.g., asdescribed below.

In some demonstrative embodiments, controller 124 may include circuitryand/or logic, e.g., one or more processors including circuitry and/orlogic, memory circuitry and/or logic, Media-Access Control (MAC)circuitry and/or logic, Physical Layer (PHY) circuitry and/or logic,and/or any other circuitry and/or logic, configured to perform thefunctionality of controller 124. Additionally or alternatively, one ormore functionalities of controller 124 may be implemented by logic,which may be executed by a machine and/or one or more processors, e.g.,as described below.

In one example, controller 124 may include circuitry and/or logic, forexample, one or more processors including circuitry and/or logic, tocause a wireless device, e.g., device 102, and/or a wireless station,e.g., a wireless STA implemented by device 102, to perform one or moreoperations, communications and/or functionalities, e.g., as describedherein.

In one example, controller 124 may perform one or more functionalitiesof a NAN engine, e.g., a NAN discovery engine (DE), for example toprocess one or more service queries and/or responses, e.g., fromapplications and/or services on devices 102, 115, 140, 150, 160, 170and/or 180, and/or one or more other devices.

In some demonstrative embodiments, device 102 may include a messageprocessor 128 configured to generate, process and/or access one ormessages communicated by device 102.

In one example, message processor 128 may be configured to generate oneor more messages to be transmitted by device 102, and/or messageprocessor 128 may be configured to access and/or to process one or moremessages received by device 102, e.g., as described below. In oneexample, message processor 128 may be configured to process transmissionof one or more messages from a wireless station, e.g., a wireless STAimplemented by device 102; and/or message processor 128 may beconfigured to process reception of one or more messages by a wirelessstation, e.g., a wireless STA implemented by device 102.

In some demonstrative embodiments, message processor 128 may includecircuitry and/or logic, e.g., one or more processors including circuitryand/or logic, memory circuitry and/or logic, Media-Access Control (MAC)circuitry and/or logic, Physical Layer (PHY) circuitry and/or logic,and/or any other circuitry and/or logic, configured to perform thefunctionality of message processor 128. Additionally or alternatively,one or more functionalities of message processor 128 may be implementedby logic, which may be executed by a machine and/or one or moreprocessors, e.g., as described below.

In one example, message processor 128 may perform one or morefunctionalities of a NAN MAC configured to generate, process and/orhandle one or more NAN messages, e.g., NAN Beacon frames and/or NANService Discovery frames.

In some demonstrative embodiments, at least part of the functionality ofmessage processor 128 may be implemented as part of radio 114.

In some demonstrative embodiments, at least part of the functionality ofmessage processor 128 may be implemented as part of controller 124.

In other embodiments, the functionality of message processor 128 may beimplemented as part of any other element of device 102.

In some demonstrative embodiments, at least part of the functionality ofcontroller 124, radio 114, and/or message processor 128 may beimplemented by an integrated circuit, for example, a chip, e.g., aSystem in Chip (SoC). In one example, the chip or SoC may be configuredto perform one or more functionalities of radio 114. For example, thechip or SoC may include one or more elements of controller 124, one ormore elements of message processor 128, and/or one or more elements ofradio 114. In one example, controller 124, message processor 128, andradio 114 may be implemented as part of the chip or SoC.

In some demonstrative embodiments, devices 102, 115, 140, 150, 160, 170and/or 180 may perform the functionality of a device or station, forexample, an awareness networking device, a NAN device, a WiFi device, aWiFi Aware device, a WFD device, a WLAN device and/or any other device,capable of discovering other devices according to a discovery protocoland/or scheme.

In some demonstrative embodiments, radio 114 may communicate overwireless communication medium 103 according to an awareness networkingscheme, for example, a discovery scheme, for example, a WiFi Awarediscovery scheme (“NAN discovery scheme”), and/or any other awarenessnetworking and/or discovery scheme, e.g., as described below.

In some demonstrative embodiments, the awareness networking scheme,e.g., NAN, may enable applications to discover services in their closeproximity. For example, the NAN technology may be a low power servicediscovery, which may, for example, scale efficiently, e.g., in denseWi-Fi environments.

In some demonstrative embodiments, a device, e.g., wirelesscommunication devices 102, 115, 140, 150, 160, 170 and/or 180, mayinclude one or more blocks and/or entities to perform network awarenessfunctionality. For example, a device, e.g., devices 102, 115, 140, 150,160, 170 and/or 180, performing the functionality of a NAN device, mayinclude a NAN MAC and/or a Discovery Engine (DE). In one example,controller 124 may be configured to perform the functionality of thediscovery engine, and/or message processor 128 may be configured toperform the functionality of the NAN MAC, e.g., as described above. Inanother example, the functionality of the NAN MAC and/or the Discoveryengine may be performed by any other element and/or entity of devices102, 115, 140, 150, 160, 170 and/or 180.

In some demonstrative embodiments, the awareness networking scheme mayinclude a discovery scheme or protocol, e.g., as described below.

In some demonstrative embodiments, devices 102, 115, 140, 150, 160, 170and/or 180 may perform a discovery process according to the awarenessnetworking scheme, for example, to discover each other and/or toestablish a wireless communication link, e.g., directional and/or highthroughput wireless communication link and/or any other link.

In some demonstrative embodiments, devices 102, 115, 140, 150, 160, 170and/or 180 may be configured to enable time synchronization betweendevices 102, 115, 140, 150, 160, 170, 180 and/or one or more otherdevices, e.g., performing the functionality of Wi-Fi stations (STAs),for example, such that STAs can discover each other more efficientlyand/or quickly.

Some demonstrative embodiments are described below with respect to a NANdiscovery scheme, and to NAN discovery frames of the NAN discoveryscheme. However, in other embodiments, any other discovery scheme and/ordiscovery frames may be used.

In some demonstrative embodiments, the discovery scheme may include aplurality of contention-based discovery windows (DWs).

In some demonstrative embodiments, communication during the DWs may beconfigured to enable time synchronization between Wi-Fi stations (STAs),e.g., devices 102, 115, 140, 150, 160, 170 and/or 180, so that STAs canfind each other more efficiently during a DW.

In some demonstrative embodiments, devices of an awareness network, e.g.a NAN network, may form one or more clusters, e.g., in order to publishand/or subscribe for services. A NAN cluster may be defined by an AnchorMaster (AM) (also referred to as a “NAN master device” or “anchordevice”). In one example, the AM may include a NAN device, which has thehighest rank in the NAN cluster.

In some demonstrative embodiments, NAN data exchange may be reflected bydiscovery frames, e.g., Publish, Subscribe and/or Follow-Up Servicediscovery frames (SDF). These frames may include action frames, whichmay be sent by a device that wishes to publish a service/application,and/or to subscribe to a published service/application at another end.

In one example, one of devices 102, 115, 140, 150, 160, 170 and/or 180,e.g., device 102, may perform the functionality of an AM. The AM may beconfigured to transmit one or more beacons. Another one of devices 102,115, 140, 150, 160, 170 and/or 180, e.g., device 140, may be configuredto receive and process the beacons.

In one example, devices 102, 115, 140, 150, 160, 170 and/or 180 mayperform the functionality of NAN devices, e.g., belonging to a NANcluster, which may share a common set of NAN parameters, for example,including a common NAN timestamp, and/or a common time period betweenconsecutive discovery windows (DWs). The NAN timestamp may becommunicated, for example, as part of a NAN beacon frame, which may becommunicated in the NAN cluster. In one example, the NAN timestamp mayinclude a Time Synchronization Function (TSF) value, for example, acluster TSF value, or any other value.

In some demonstrative embodiments, devices 102, 115, 140, 150, 160, 170and/or 180 may be configured to discover one another over a predefinedcommunication channel (“the social channel”). In one example, theChannel 6 in the 2.4 GHz band may be defined as the NAN social channel.Any other channel may be used as the social channel.

In some demonstrative embodiments, devices 102, 115, 140, 150, 160, 170and/or 180 may transmit discovery frames, e.g., SDFs, during theplurality of DWs, e.g., over the social channel. For example the NAN AMmay advertize the time of the DW, during which NAN devices may exchangeSDFs.

In one example, devices 102, 115, 140, 150, 160, 170 and/or 180 maytransmit the discovery frames to discover each other, for example, toenable using the one or more services provided by applications 125and/or 126.

In some demonstrative embodiments, devices 102, 115, 140, 150, 160, 170and/or 180 may communicate during a DW according to a contentionmechanism. For example, devices 102, 115, 140, 150, 160, 170 and/or 180may check whether or not a channel is unoccupied prior to an attempt totransmit a discovery frame during the discovery window.

In some demonstrative embodiments, a device of devices 102, 115, 140,150, 160, 170 and/or 180, e.g., device 102, may not transmit thediscovery frame during the DW, e.g., if the channel is occupied. In somedemonstrative embodiments, device 102 may transmit the discovery frameduring the DW, e.g., if the channel is unoccupied.

In some embodiments, the discovery frame may be transmitted as a groupaddressed, e.g., broadcast or multicast, discovery frame. In otherembodiments, the discovery frame may be transmitted as any other type offrame.

In some demonstrative embodiments, the discovery frame may not requirean acknowledgement frame. According to these embodiments, a transmitterof the discovery frame may not backoff a transmission of the discoveryframe.

In some demonstrative embodiments, the discovery frame transmitted bydevice 102 during the DW may be configured to enable other devices orservices that are running on other devices to discover the services ondevice 102.

In some demonstrative embodiments, devices of system 100 may utilizeavailability information, e.g., in the form of an Availability IntervalBitmap and/or Further Availability Map, for example, to allow a deviceof devices 102, 115, 140, 150, 160, 170 and/or 180, to advertise itsavailability, for example, in terms of at least one channel and one ormore timeslots, during which the device may be available, e.g., active(“awake”), for example, to perform post NAN activities.

In one example, the availability information may be communicated as partof an Availability Attribute, e.g., including a 32-bit bitmap for 32timeslots, for example, wherein each timeslot is 16 milliseconds (ms)long. For example, each bit that is not zero may represent a timeslot,during which a device sending the Availability attribute is to awake andavailable to send and/or receive data in a specified method.

In some demonstrative embodiments, devices 102, 115, 140, 150, 160, 170and/or 180 may be part of an awareness cluster, e.g., a NAN cluster.

In some demonstrative embodiments, devices 102, 115, 140, 150, 160, 170and/or 180 may be configured to enable data transmission for a serviceamong multiple devices, for example, using at least one data path group,e.g., an awareness data path group, for example, a Wi-Fi Aware datapath, e.g., after service discovery.

In some demonstrative embodiments, devices 102, 115, 140, 150, 160, 170and/or 180 may be configured to enable construction of at least one datapath group, for example, based on constraints of security, mediumefficiency, and/or any other constraint, criterion and/or requirement.In one example, a service may require secure data transmission, and/or adevice that subscribes to different services may need to efficientlytransmit and receive the data related to the different services.

In some demonstrative embodiments, devices 102, 115, 140, 150, 160, 170and/or 180 may be configured to communicate according to a networkarchitecture, which may include at least one data path group, which maybe, for example, under the framework of the awareness cluster, e.g., aWi-Fi Aware cluster, for example, to enable to address the issues ofsecurity and/or efficiency, and/or any other issues.

In one example, devices 102, 115, 140, 150, and/or 160 may be part of adata path group 109 within the awareness cluster, for example, having afirst common or shared Schedule of Radio Resources (SRR), e.g., asdescribed below.

In another example, devices 170 and/or 180 may be part of a data pathgroup 189 within the awareness cluster, for example, having a secondcommon or shared SRR, e.g., as described below.

In some demonstrative embodiments, devices of the awareness cluster,e.g., including devices 102, 115, 140, 150, 160, 170 and/or 180, may bedivided into at least two layers, for example, a data path group layer,and a service data group layer, e.g., as described below.

In some demonstrative embodiments, the phrases “data path group” and/or“service data group” may be used herein to provide a high-level conceptof the network architecture. Any additional or alternative names, termsor phrases may be used with respect to these concepts.

In one example, the data path group layer may include data path group109, e.g., including devices 102, 115, 140, 150, and/or 160; and datapath group 189, e.g., including devices 170 and/or 189.

In some demonstrative embodiments, devices of the awareness cluster,e.g., including devices 102, 115, 140, 150, 160, 170 and/or 180, maybelong to at least one service data group.

In one example, the service data group layer may include a service datagroup 149, e.g., including devices 102, 115 and/or 140; a service datagroup 169, e.g., including devices 102, 150 and/or 160; and/or a servicedata group 179, e.g., including devices 170 and 180.

In some demonstrative embodiments, a service data group may includedevices subscribed to a common service and/or application.

In some demonstrative embodiments, at least one service data group,e.g., service data groups 149 and/or 169 may belong to the same datapath group, e.g., data path group 109.

Reference is made to FIG. 2, which schematically illustrates a networkarchitecture 200, in accordance with some demonstrative embodiments.

As shown in FIG. 2, network architecture may include an awarenesscluster 202 including a plurality of devices. For example, awarenesscluster 202 may include devices 102, 115, 140, 150, 160, 170 and/or 180(FIG. 1).

As shown in FIG. 2, at least one data path group 204 may be formed byone or more devices of the plurality of devices of awareness cluster202. For example, data path group may perform the functionality of datapath group 109 (FIG. 1).

As shown in FIG. 2, at least one service data group 206 may be formed bydevices of data path group 204. For example, service data group 206 mayperform the functionality of service data group 149 (FIG. 1).

In some demonstrative embodiments, the network architecture 200including the data path group 204, e.g., formed under the awarenesscluster 202, and/or the service data group 206, e.g., formed under thedata path group 204, may enable to provide, for example, at leastincreased medium efficiency, and/or a secure data path, e.g., asdescribed below.

In some demonstrative embodiments, data path group 204 may includedevices with a common Schedule of Radio Resources (SRR), for example,the same time schedule and/or frequency hopping schedule, e.g., in aperiod of a pattern repetition.

In one example, the availability information of a device may representthe SRR of the device. The SRR may be represented, defined, and/ordetermined in any other manner.

In some demonstrative embodiments, devices with the same SRR may form,and/or may be part of, data path group 204.

In some demonstrative embodiments, forming of data path group 204 mayenable, for example, to improve efficiency of medium access, forexample, such that a channel switching delay and/or an awake time may bereduced, e.g., minimized.

In some demonstrative embodiments, the period of pattern repetition mayinclude, for example, a period of a Discovery Window in the awarenesscluster, e.g., a period of a DW in a Wi-Fi Aware cluster.

In some demonstrative embodiments, service data group 206 may be definedwith respect to devices that subscribe to the same service.

In some demonstrative embodiments, a plurality of devices that subscribeto the same service may form service data group 206.

In some demonstrative embodiments, service data group 206 may enable,for example, to provide a service access policy, e.g. security, for aservice.

In some demonstrative embodiments, forming of service data group 206within data path group 204 may enable devices of service data group 206to share a common SRR, e.g., the SRR of data path group 204.

In some demonstrative embodiments, sharing the common SRR, e.g., bydevices of service data group 206, may enable, for example, an efficientcommunication of a device and/or an efficient utilization of the mediumby the device, e.g., as described below with reference to FIGS. 3 and/or4.

Reference is made to FIG. 3, which schematically illustrates timing andfrequency schedules of a first service data group (group A) and a secondservice data group (group B), in accordance with some demonstrativeembodiments. For example, group A may perform the functionality ofservice data group 206 (FIG. 2), and/or service data group 149 (FIG. 1);and/or group B may perform the functionality of service data group 179(FIG. 1).

In some demonstrative embodiments, service data group A and service datagroup B may follow different schedules, e.g., having different timingand/or frequency hopping patterns for example, if service data group Aand service data group B are assigned to different data path groups.

In one example, service data group A may share a first common SRR andservice data group B may share a second, e.g., different, SRR, forexample, if service data group A is within data path group 109 (FIG. 1),and/or service data group B is within data path group 189 (FIG. 1).

As shown in FIG. 3, as a result of the different schedules of servicedata group A and service data group B, a device belonging to both of theservice data groups A and B may be required to switch channels six timesin a period of pattern repetition 301, for example, if the service datagroups A and B communicate according to different SRRs over threechannels, e.g., channel A, channel B and channel C.

For example, as shown in FIG. 3, during the period of pattern repetition301, the device may be required to communicate over channel A withservice data group A during a time period 302; the device may berequired to switch from channel A to channel C, e.g., to communicateover channel C with service data group B during a time period 304; thedevice may be required to switch from channel C to channel B, e.g., tocommunicate over channel B with service data group A during a timeperiod 306; the device may be required to switch from channel B tochannel A, e.g., to communicate over channel A with service data group Bduring a time period 308; the device may be required to switch fromchannel A to channel C, e.g., to communicate over channel C with servicedata group A during a time period 310; the device may be required toswitch from channel C to channel B, e.g., to communicate over channel Bwith service data group B during a time period 312; and/or the devicemay be required to switch from channel B to channel A, e.g., tocommunicate over channel A with service data group A during a first timeperiod of a subsequent period of pattern repetition.

In some demonstrative embodiments, this increased rate of channelswitching may not enable an efficient communication of the device and/oran efficient utilization of the medium.

Reference is made to FIG. 4, which schematically illustrates timing andfrequency schedules of a first service data group (group A) and a secondservice data group (group B), in accordance with some demonstrativeembodiments. For example, group A may perform the functionality ofservice data group 206 (FIG. 2), and/or service data group 149 (FIG. 1);and/or group B may perform the functionality of service data group 169(FIG. 1).

In some demonstrative embodiments, service data group A and service datagroup B may follow the same schedule, e.g., having the same timing andfrequency hopping patterns, for example, if service data group A andservice data group B are assigned to the same data path group.

In one example, both service data group A and service data group B mayshare the same common SRR, for example, if service data groups A and Bassigned to the same data path group 109 (FIG. 1).

As shown in FIG. 4, a device belonging to both the service data group Aand the service data group B may be required to switch channels only 3times in a period of pattern repetition 401.

For example, as shown in FIG. 4, during the period of pattern repetition401, the device may communicate over channel A with both service datagroups A and B during a time period 402; to the device may switch fromchannel A to channel B, e.g., to communicate over channel B with bothservice data groups A and B during a time period 404; the device mayswitch from channel B to channel C, e.g., to communicate over channel Cwith both service data groups A and B during a time period 406; and/orthe device may switch from channel C to channel A, e.g., to communicateover channel A with both service data groups A and B during a first timeperiod of a subsequent period of pattern repetition.

In some demonstrative embodiments, this reduced rate of channelswitching may enable an efficient communication of the device and/or anefficient utilization of the medium, e.g., compared to the channelswitching of FIG. 3.

Referring back to FIG. 1, some demonstrative embodiments may enabledevices in a service data group to share a common SRR, e.g., an SRR ofthe data path group including the devices of the service path group.

In one example, devices 102, 115, and/or 140 of service data group 149may share an SRR of data path group 109.

In some demonstrative embodiments, device 102 may communicate during oneor more Discovery Windows (DW) of the awareness cluster includingwireless communication devices 102, 115, 140, 150, 160, 170 and/or 180.

In some demonstrative embodiments, device 102 may communicate with oneor more devices of at least one data path group 109. For example, device102 may communicate with devices 115, 140, 150, and/or 160.

In some demonstrative embodiments, the data path group 109 may includedevices of the awareness cluster, which may have a common SRR.

In some demonstrative embodiments, the common SRR may include timing andchannel resources, e.g., as described above.

In some demonstrative embodiments, device 102 may be configured tocommunicate with the devices of the service data group 149 according toa security policy. For example, device 102 may communicate with devices115 and/or 140 according to a security policy of application 125.

In some demonstrative embodiments, device 102 may be configured tocommunicate with the devices of the service data group 149 according toan access policy. For example, device 102 may communicate with devices115 and/or 140 according to an access policy of application 125.

In some demonstrative embodiments, device 102 may communicate with oneor more devices of the at least one service data group 149.

In some demonstrative embodiments, service data group 149 may includedevices of data path group 109 being subscribed to a common service. Forexample, service data group 149 may include devices 102, 115 and 140,which may have subscribed to application 125.

In some demonstrative embodiments, device 102 may communicate withdevices of a plurality of service data groups within the data path group109.

In some demonstrative embodiments, the plurality of service data groupsmay share the common SRR, e.g., the SRR of data path group 109. Forexample, device 102 may communicate with devices 150 and/or 160 ofservice data group 169, e.g., within data path group 109.

In some demonstrative embodiments, device 102 may communicate withdevices of a plurality of data path groups belonging to the awarenesscluster. For example, device 102 may communicate with devices 170 and/or180 of data path group 189, which belong to the awareness cluster, e.g.,including wireless communication devices 102, 115, 140, 150, 160, 170and/or 180.

In some demonstrative embodiments, device 102 may be configured to jointhe service data group 149.

In one example, device 140 may form service data group 149 includingdevices 115 and 140, for example, to share an application on device 140.According to this example, device 102 may be configured to join theservice data group 149, for example, to share and/or to utilize anapplication on device 140.

In some demonstrative embodiments, device 102 may be configured to formthe service data group 149.

In one example, device 102 may form service data group 149 includingdevices 102, 115 and/or 140, for example, to share application 126 ondevice 102 between devices 102, 115 and/or 140.

In some demonstrative embodiments, device 102 may be configured to forma data path group including the service data group.

In one example, device 102 may form a data path group including servicedata group 149, e.g. including devices 102, 115 and/or 140, for example,to share application 126 between devices 102, 115 and/or 140, e.g.,using a common SRR.

In some demonstrative embodiments, device 102 may be configured to formservice data group 149 in an existing data path group.

In one example, device 140 may form data path group 109 includingdevices 102, 115, 140, 150 and/or 160, and device 102 may form servicedata group 149, e.g., after data path group 109 is formed.

Reference is made to FIG. 5, which schematically illustratesrelationships between a service data group 506, a data path group 504,and a cluster 502, in accordance with some demonstrative embodiments.For example, service data group 506 may perform the functionality ofservice data group 149 (FIG. 1), and/or service data group 206 (FIG. 2);data path group 504 may perform the functionality of data path group 109(FIG. 1), and/or data path group 204 (FIG. 2); and/or cluster 502 mayperform the functionality of cluster 202 (FIG. 2).

In some demonstrative embodiments, as shown in FIG. 5, devices in datapath group 504 may belong to the same awareness cluster 502, e.g., Wi-Fiaware cluster, for example, in order to utilize the timingsynchronization and service discovery framework of cluster 502.

In some demonstrative embodiments, devices in service data group 506 maybelong to the same data path group 504, for example, to utilize the SRRof data path group 504 and/or to facilitate secure data exchange, e.g.,based on a security policy of data path group 504.

In some demonstrative embodiments, the data path group 504 and/or theservice data group 506 may have one or more functionalities, e.g., asdescribed below.

In some demonstrative embodiments, devices of data path group 504 mayhave an available path for data transmission, e.g., SRR, defined for thedevices in the data path group 504.

In some demonstrative embodiments, devices in data path group 504 mayhave one or more properties, e.g., as described below.

In some demonstrative embodiments, devices in data path group 504 mayhave a basic schedule of timing window and frequency hopping pattern.

In some demonstrative embodiments, devices in data path group 504 mayhave a limited number of channels for frequency hopping.

In some demonstrative embodiments, devices in data path group 504 mayhave additional schedules of timing window and/or frequency hoppingpattern for a subset of devices in the data path group, e.g., a sub-datapath group in a data path group.

In some demonstrative embodiments, devices in data path group 504 mayinitiate the change of the SRR.

In some demonstrative embodiments, devices that may be subscribed to asame service may be in service data group 506.

In some demonstrative embodiments, the service data group 506 may haveone or more properties, e.g., as described below.

In some demonstrative embodiments, the devices in service data group 506may have an access policy for service data transmission.

In some demonstrative embodiments, the devices in service data group 506may have a security policy, or may not have a security policy.

In some demonstrative embodiments, the devices in service data group 506may use broadcast, multicast, or unicast transmission, e.g., tocommunicate between devices of service data group 506.

In some demonstrative embodiments, the devices in service data group 506may use multi-hop or relay transmission e.g., to communicate betweendevices of service data group 506.

In some demonstrative embodiments, the devices in service data group 506may be limited to only one-hop transmission.

In some demonstrative embodiments, a plurality of service data groups506 may be established in data path group 504.

In some demonstrative embodiments, service data group 506 and/or datapath group 504 may be initiated, defined, and/or formed, for example,using one or more of the operations described below. However, theoperations, e.g., as described herein, may not be limited by anymechanism to initiate the group.

In some demonstrative embodiments, service data group 506 may be createdwith data path group 504 simultaneously, e.g., as described above.

In one example, a device may start service data group 506 and may definean SRR for the service data group 506. Accordingly, data path group 504may also be created, e.g., with respect to one or more devices havingthe defined SRR.

In some demonstrative embodiments, service data group 506 may be formedin a new data path group 504.

In some demonstrative embodiments, service data group 506 may be createdin a data path group.

For example, service data group 506 may be formed in an existing datapath group 504. According to this example, devices of data path group504 may be able to form another service data group in data path group504.

In some demonstrative embodiments, service data group 506 may beinitiated by any device, e.g., wireless communication devices 102, 115,140, 150, 160, 170 and/or 180.

In some demonstrative embodiments, using the relationship betweenservice data group 506, data path group 504, and cluster 502, e.g., asdescribed above, may enable efficient utilization of WM 103 (FIG. 1),and/or efficient communication between wireless communication devices,e.g., devices 102, 115, 140, 150, 160, 170 and/or 180 (FIG. 1), sharingone or more services within a data path group.

Reference is made to FIG. 6, which schematically illustrates a method ofcommunicating in an awareness cluster, in accordance with somedemonstrative embodiments. For example, one or more of the operation ofFIG. 6 may be performed by one or more elements of a system, system 100(FIG. 1), a device, wireless communication devices 102, 115, 140, 150,160, 170 and/or 180 (FIG. 1), a controller, e.g., controller 124 (FIG.1); a radio, e.g., radio 114 (FIG. 1); and/or a message processor, e.g.,message processor 128 (FIG. 1).

As indicated at block 602, the method may include communicating duringone or more Discovery Windows (DW) of an awareness cluster. For example,device 102 (FIG. 1) may communicate during one or more DWs of theawareness cluster including wireless communication devices 102, 115,140, 150, 160, 170 and/or 180 (FIG. 1), e.g., as described above.

As indicated at block 604, the method may include communicating with oneor more devices of at least one data path group, the data path groupincluding devices of the awareness cluster and having a common scheduleof radio resources (SRR). For example, device 102 (FIG. 1) maycommunicate with one or more devices of data path group 109 (FIG. 1)having a common schedule SRR, e.g., as described above.

As indicated at block 606, the method may include communicating with oneor more devices of at least one service data group, the service datagroup including devices of the data path group being subscribed to acommon service. For example, device 102 (FIG. 1) may communicate withdevices 140 and/or 115 (FIG. 1), e.g., of service data group 149 (FIG.1), which may be subscribed to a service provided by application 125(FIG. 1), e.g., as described above.

As indicated at block 608, communicating with one or more devices of atleast one service data group may include communicating with devices of aplurality of service data groups within the data path group, theplurality of service data groups sharing the common SRR. For example,device 102 (FIG. 1) may communicate with devices 150 and/or 160 (FIG. 1)of service data group 169 (FIG. 1), as well as with devices 115 and/or140 (FIG. 1) of service data group 149 (FIG. 1), e.g., sharing thecommon SRR of data path group 109 (FIG. 1), e.g., as described above.

As indicated at block 610, the method may include joining the servicedata group. For example, device 102 (FIG. 1) may join service data group149 (FIG. 1), e.g., as described above.

As indicated at block 612, the method may include forming the servicedata group. For example, device 102 (FIG. 1) may form service data group149 (FIG. 1), e.g., as described above.

Reference is made to FIG. 7, which schematically illustrates a productof manufacture 700, in accordance with some demonstrative embodiments.Product 700 may include a non-transitory machine-readable storage medium702 to store logic 704, which may be used, for example, to perform atleast part of the functionality of devices 102, 115, 140, 150, 160, 170and/or 180 (FIG. 1), radio 114 (FIG. 1), transmitter 118 (FIG. 1),receiver 116 (FIG. 1), controller 124, message processor 128 (FIG. 1),and/or to perform one or more operations and/or functionalities of theFIGS. 2, 3, 4, 5, and/or 6. The phrase “non-transitory machine-readablemedium” is directed to include all computer-readable media, with thesole exception being a transitory propagating signal.

In some demonstrative embodiments, product 700 and/or machine-readablestorage medium 702 may include one or more types of computer-readablestorage media capable of storing data, including volatile memory,non-volatile memory, removable or non-removable memory, erasable ornon-erasable memory, writeable or re-writeable memory, and the like. Forexample, machine-readable storage medium 702 may include, RAM, DRAM,Double-Data-Rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM,programmable ROM (PROM), erasable programmable ROM (EPROM), electricallyerasable programmable ROM (EEPROM), Compact Disk ROM (CD-ROM), CompactDisk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), flash memory(e.g., NOR or NAND flash memory), content addressable memory (CAM),polymer memory, phase-change memory, ferroelectric memory,silicon-oxide-nitride-oxide-silicon (SONOS) memory, a disk, a floppydisk, a hard drive, an optical disk, a magnetic disk, a card, a magneticcard, an optical card, a tape, a cassette, and the like. Thecomputer-readable storage media may include any suitable media involvedwith downloading or transferring a computer program from a remotecomputer to a requesting computer carried by data signals embodied in acarrier wave or other propagation medium through a communication link,e.g., a modem, radio or network connection.

In some demonstrative embodiments, logic 704 may include instructions,data, and/or code, which, if executed by a machine, may cause themachine to perform a method, process and/or operations as describedherein. The machine may include, for example, any suitable processingplatform, computing platform, computing device, processing device,computing system, processing system, computer, processor, or the like,and may be implemented using any suitable combination of hardware,software, firmware, and the like.

In some demonstrative embodiments, logic 704 may include, or may beimplemented as, software, a software module, an application, a program,a subroutine, instructions, an instruction set, computing code, words,values, symbols, and the like. The instructions may include any suitabletype of code, such as source code, compiled code, interpreted code,executable code, static code, dynamic code, and the like. Theinstructions may be implemented according to a predefined computerlanguage, manner or syntax, for instructing a processor to perform acertain function. The instructions may be implemented using any suitablehigh-level, low-level, object-oriented, visual, compiled and/orinterpreted programming language, such as C, C++, Java, BASIC, Matlab,Pascal, Visual BASIC, assembly language, machine code, and the like.

EXAMPLES

The following examples pertain to further embodiments.

Example 1 includes an apparatus comprising circuitry configured to causean awareness networking device to communicate during one or moreDiscovery Windows (DW) of an awareness cluster; communicate with one ormore devices of at least one data path group, the data path groupcomprising devices of the awareness cluster and having a common scheduleof radio resources (SRR); and communicate with one or more devices of atleast one service data group, the service data group comprising devicesof the data path group being subscribed to a common service.

Example 2 includes the subject matter of Example 1, and optionally,being configured to cause the awareness networking device to communicatewith devices of a plurality of service data groups within the data pathgroup, the plurality of service data groups sharing the common SRR.

Example 3 includes the subject matter of Example 1 or 2, and optionally,being configured to cause the awareness networking device to communicatewith devices of a plurality of data path groups belonging to theawareness cluster.

Example 4 includes the subject matter of any one of Examples 1-3, andoptionally, being configured to cause the awareness networking device tojoin the service data group.

Example 5 includes the subject matter of any one of Examples 1-4, andoptionally, being configured to cause the awareness networking device toform the service data group.

Example 6 includes the subject matter of Example 5, and optionally,being configured to cause the awareness networking device to form a datapath group comprising the service data group.

Example 7 includes the subject matter of Example 5, and optionally,being configured to cause the awareness networking device to form theservice data group in an existing data path group.

Example 8 includes the subject matter of any one of Examples 1-7, andoptionally, wherein the SRR comprises timing and channel resources.

Example 9 includes the subject matter of any one of Examples 1-8, andoptionally, being configured to cause the awareness networking device tocommunicate with the devices of the service data group according to asecurity policy.

Example 10 includes the subject matter of any one of Examples 1-9, andoptionally, being configured to cause the awareness networking device tocommunicate with the devices of the service data group according to anaccess policy.

Example 11 includes the subject matter of any one of Examples 1-10, andoptionally, wherein the awareness networking device comprises a NeighborAwareness Networking (NAN) device, and wherein the awareness clustercomprises a NAN cluster.

Example 12 includes the subject matter of any one of Examples 1-11, andoptionally, comprising a radio, one or more antennas, a memory, and aprocessor.

Example 13 includes a system comprising an awareness networking device,the awareness networking device comprising one or more antennas; amemory; a processor; and a radio to communicate during one or moreDiscovery Windows (DW) of an awareness cluster; to communicate with oneor more devices of at least one data path group, the data path groupcomprising devices of the awareness cluster and having a common scheduleof radio resources (SRR); and to communicate with one or more devices ofat least one service data group, the service data group comprisingdevices of the data path group being subscribed to a common service.

Example 14 includes the subject matter of Example 13, and optionally,wherein the awareness networking device is to communicate with devicesof a plurality of service data groups within the data path group, theplurality of service data groups sharing the common SRR.

Example 15 includes the subject matter of Example 13 or 14, andoptionally, wherein the awareness networking device is to communicatewith devices of a plurality of data path groups belonging to theawareness cluster.

Example 16 includes the subject matter of any one of Examples 13-15, andoptionally, wherein the awareness networking device is to join theservice data group.

Example 17 includes the subject matter of any one of Examples 13-16, andoptionally, wherein the awareness networking device is to form theservice data group.

Example 18 includes the subject matter of Example 17, and optionally,wherein the awareness networking device is to form a data path groupcomprising the service data group.

Example 19 includes the subject matter of Example 17, and optionally,wherein the awareness networking device is to form the service datagroup in an existing data path group.

Example 20 includes the subject matter of any one of Examples 13-19, andoptionally, wherein the SRR comprises timing and channel resources.

Example 21 includes the subject matter of any one of Examples 13-20, andoptionally, wherein the awareness networking device is to communicatewith the devices of the service data group according to a securitypolicy.

Example 22 includes the subject matter of any one of Examples 13-21, andoptionally, wherein the awareness networking device is to communicatewith the devices of the service data group according to an accesspolicy.

Example 23 includes the subject matter of any one of Examples 13-22, andoptionally, wherein the awareness networking device comprises a NeighborAwareness Networking (NAN) device, and wherein the awareness clustercomprises a NAN cluster.

Example 24 includes a method to be performed at an awareness networkingdevice, the method comprising communicating during one or more DiscoveryWindows (DW) of an awareness cluster; communicating with one or moredevices of at least one data path group, the data path group comprisingdevices of the awareness cluster and having a common schedule of radioresources (SRR); and communicating with one or more devices of at leastone service data group, the service data group comprising devices of thedata path group being subscribed to a common service.

Example 25 includes the subject matter of Example 24, and optionally,comprising communicating with devices of a plurality of service datagroups within the data path group, the plurality of service data groupssharing the common SRR.

Example 26 includes the subject matter of Example 24 or 25, andoptionally, comprising communicating with devices of a plurality of datapath groups belonging to the awareness cluster.

Example 27 includes the subject matter of any one of Examples 24-26, andoptionally, comprising joining the service data group.

Example 28 includes the subject matter of any one of Examples 24-27, andoptionally, comprising forming the service data group.

Example 29 includes the subject matter of Example 28, and optionally,comprising forming a data path group comprising the service data group.

Example 30 includes the subject matter of Example 28, and optionally,comprising forming the service data group in an existing data pathgroup.

Example 31 includes the subject matter of any one of Examples 24-30, andoptionally, wherein the SRR comprises timing and channel resources.

Example 32 includes the subject matter of any one of Examples 24-31, andoptionally, comprising communicating with the devices of the servicedata group according to a security policy.

Example 33 includes the subject matter of any one of Examples 24-32, andoptionally, comprising communicating with the devices of the servicedata group according to an access policy.

Example 34 includes the subject matter of any one of Examples 24-33, andoptionally, wherein the awareness networking device comprises a NeighborAwareness Networking (NAN) device, and wherein the awareness clustercomprises a NAN cluster.

Example 35 includes a product comprising one or more tangiblecomputer-readable non-transitory storage media comprisingcomputer-executable instructions operable to, when executed by at leastone computer processor, enable the at least one computer processor toimplement one or more operations at an awareness networking device, theoperations comprising communicating during one or more Discovery Windows(DW) of an awareness cluster; communicating with one or more devices ofat least one data path group, the data path group comprising devices ofthe awareness cluster and having a common schedule of radio resources(SRR); and communicating with one or more devices of at least oneservice data group, the service data group comprising devices of thedata path group being subscribed to a common service.

Example 36 includes the subject matter of Example 35, and optionally,wherein the operations comprise communicating with devices of aplurality of service data groups within the data path group, theplurality of service data groups sharing the common SRR.

Example 37 includes the subject matter of Example 35 or 36, andoptionally, wherein the operations comprise communicating with devicesof a plurality of data path groups belonging to the awareness cluster.

Example 38 includes the subject matter of any one of Examples 35-37, andoptionally, wherein the operations comprise joining the service datagroup.

Example 39 includes the subject matter of any one of Examples 35-38, andoptionally, wherein the operations comprise forming the service datagroup.

Example 40 includes the subject matter of Example 39, and optionally,wherein the operations comprise forming a data path group comprising theservice data group.

Example 41 includes the subject matter of Example 39, and optionally,wherein the operations comprise forming the service data group in anexisting data path group.

Example 42 includes the subject matter of any one of Examples 35-41, andoptionally, wherein the SRR comprises timing and channel resources.

Example 43 includes the subject matter of any one of Examples 35-42, andoptionally, wherein the operations comprise communicating with thedevices of the service data group according to a security policy.

Example 44 includes the subject matter of any one of Examples 35-43, andoptionally, wherein the operations comprise communicating with thedevices of the service data group according to an access policy.

Example 45 includes the subject matter of any one of Examples 35-44, andoptionally, wherein the awareness networking device comprises a NeighborAwareness Networking (NAN) device, and wherein the awareness clustercomprises a NAN cluster.

Example 46 includes an apparatus of wireless communication by anawareness networking device, the apparatus comprising means forcommunicating during one or more Discovery Windows (DW) of an awarenesscluster; means for communicating with one or more devices of at leastone data path group, the data path group comprising devices of theawareness cluster and having a common schedule of radio resources (SRR);and means for communicating with one or more devices of at least oneservice data group, the service data group comprising devices of thedata path group being subscribed to a common service.

Example 47 includes the subject matter of Example 46, and optionally,comprising means for communicating with devices of a plurality ofservice data groups within the data path group, the plurality of servicedata groups sharing the common SRR.

Example 48 includes the subject matter of Example 46 or 47, andoptionally, comprising means for communicating with devices of aplurality of data path groups belonging to the awareness cluster.

Example 49 includes the subject matter of any one of Examples 46-48, andoptionally, comprising means for joining the service data group.

Example 50 includes the subject matter of any one of Examples 46-49, andoptionally, comprising means for forming the service data group.

Example 51 includes the subject matter of Example 50, and optionally,comprising means for forming a data path group comprising the servicedata group.

Example 52 includes the subject matter of Example 50, and optionally,comprising means for forming the service data group in an existing datapath group.

Example 53 includes the subject matter of any one of Examples 46-52, andoptionally, wherein the SRR comprises timing and channel resources.

Example 54 includes the subject matter of any one of Examples 46-53, andoptionally, comprising means for communicating with the devices of theservice data group according to a security policy.

Example 55 includes the subject matter of any one of Examples 46-54, andoptionally, comprising means for communicating with the devices of theservice data group according to an access policy.

Example 56 includes the subject matter of any one of Examples 46-55, andoptionally, wherein the awareness networking device comprises a NeighborAwareness Networking (NAN) device, and wherein the awareness clustercomprises a NAN cluster.

Functions, operations, components and/or features described herein withreference to one or more embodiments, may be combined with, or may beutilized in combination with, one or more other functions, operations,components and/or features described herein with reference to one ormore other embodiments, or vice versa.

While certain features have been illustrated and described herein, manymodifications, substitutions, changes, and equivalents may occur tothose skilled in the art. It is, therefore, to be understood that theappended claims are intended to cover all such modifications and changesas fall within the true spirit of the disclosure.

What is claimed is:
 1. An apparatus comprising: a memory; and aprocessor configured to cause a first Neighbor Awareness Networking(NAN) device to: communicate one or more NAN Service Discovery Frames(SDFs) during one or more Discovery Windows (DWs) of a NAN cluster, theNAN cluster comprising a plurality of NAN devices sharing a commontiming of the DWs; and communicate data with a second NAN deviceaccording to a common schedule of resources shared by a NAN data groupin said NAN cluster, the NAN data group comprising at least the firstand second NAN devices.
 2. The apparatus of claim 1 configured to causethe first NAN device to communicate the data with the second NAN deviceaccording to a first common schedule of resources shared by a first NANdata group in said NAN cluster, and to communicate data with a third NANdevice according to a second common schedule of resources shared by asecond NAN data group in said NAN cluster, the second NAN data groupcomprising at least the first and third NAN devices.
 3. The apparatus ofclaim 2, wherein the first common schedule of resources is differentfrom the second common schedule of resources.
 4. The apparatus of claim1 configured to cause the first NAN device to communicate data with athird NAN device according to the common schedule of resources shared bythe NAN data group, the NAN data group comprising at least the first,second and third NAN devices.
 5. The apparatus of claim 1 configured tocause the first NAN device to form the NAN data group.
 6. The apparatusof claim 1 configured to cause the first NAN device to communicate thedata with the second NAN device in a unicast communication.
 7. Theapparatus of claim 1 configured to cause the first NAN device toestablish a link to communicate the data with the second NAN deviceaccording to the common schedule of resources.
 8. The apparatus of claim1, wherein the plurality of NAN devices in the NAN cluster share acommon Time Synchronization function (TSF).
 9. The apparatus of claim 1,wherein the common schedule of resources comprises one or more timeslots over one or more channels.
 10. The apparatus of claim 1, whereinthe common schedule of resources comprises one or more first time slotsover a first channel and one or more second time slots over a secondchannel.
 11. The apparatus of claim 1 comprising a radio.
 12. Theapparatus of claim 1 comprising one or more antennas.
 13. A productcomprising one or more tangible computer-readable non-transitory storagemedia comprising computer-executable instructions operable to, whenexecuted by at least one processor, enable the at least one processor tocause a first Neighbor Awareness Networking (NAN) device to: communicateone or more NAN Service Discovery Frames (SDFs) during one or moreDiscovery Windows (DWs) of a NAN cluster, the NAN cluster comprising aplurality of NAN devices sharing a common timing of the DWs; andcommunicate data with a second NAN device according to a common scheduleof resources shared by a NAN data group in said NAN cluster, the NANdata group comprising at least the first and second NAN devices.
 14. Theproduct of claim 13, wherein the instructions, when executed, cause thefirst NAN device to communicate the data with the second NAN deviceaccording to a first common schedule of resources shared by a first NANdata group in said NAN cluster, and to communicate data with a third NANdevice according to a second common schedule of resources shared by asecond NAN data group in said NAN cluster, the second NAN data groupcomprising at least the first and third NAN devices.
 15. The product ofclaim 14, wherein the first common schedule of resources is differentfrom the second common schedule of resources.
 16. The product of claim13, wherein the instructions, when executed, cause the first NAN deviceto communicate data with a third NAN device according to the commonschedule of resources shared by the NAN data group, the NAN data groupcomprising at least the first, second and third NAN devices.
 17. Theproduct of claim 13, wherein the instructions, when executed, cause thefirst NAN device to form the NAN data group.
 18. The product of claim13, wherein the instructions, when executed, cause the first NAN deviceto communicate the data with the second NAN device in a unicastcommunication.
 19. The product of claim 13, wherein the instructions,when executed, cause the first NAN device to establish a link tocommunicate the data with the second NAN device according to the commonschedule of resources.
 20. The product of claim 13, wherein theplurality of NAN devices in the NAN cluster share a common TimeSynchronization function (TSF).
 21. The product of claim 13, wherein thecommon schedule of resources comprises one or more time slots over oneor more channels.
 22. The product of claim 13, wherein the commonschedule of resources comprises one or more first time slots over afirst channel and one or more second time slots over a second channel.23. An apparatus comprising: means for causing a first NeighborAwareness Networking (NAN) device to communicate one or more NAN ServiceDiscovery Frames (SDFs) during one or more Discovery Windows (DWs) of aNAN cluster, the NAN cluster comprising a plurality of NAN devicessharing a common timing of the DWs; and means for causing the first NANdevice to communicate data with a second NAN device according to acommon schedule of resources shared by a NAN data group in said NANcluster, the NAN data group comprising at least the first and second NANdevices.
 24. The apparatus of claim 23 comprising means for causing thefirst NAN device to communicate the data with the second NAN deviceaccording to a first common schedule of resources shared by a first NANdata group in said NAN cluster, and to communicate data with a third NANdevice according to a second common schedule of resources shared by asecond NAN data group in said NAN cluster, the second NAN data groupcomprising at least the first and third NAN devices.
 25. The apparatusof claim 23 comprising means for causing the first NAN device tocommunicate data with a third NAN device according to the commonschedule of resources shared by the NAN data group, the NAN data groupcomprising at least the first, second and third NAN devices.